2014-01-28 - 6474 - Spec - SNC Inbound delivery Enhancement #SNCProject #Delivery #Shipping #ABAPSNC #abapidoc #abapexit

SPECIFICATIONS

6474 -Spec-Enhancement for Inbound delivery

Purpose

The enhancement is used to update Customer Partners , Incoterm and Route value into Inbound delivery so that data is populated into ASN for Customer

Admin Info

Purpose	6474 - Enhancement for Inbound delivery
Requested By	Rahul Attarde
Spec Created By	Venkat K , Vengal Rao
Spec Created Date	01/28/2014
Spec QA by	Vengal Rao , Siba Prasad
Objects	MV50AFZ1
Document Status	Complete

References

Prior Tickets

N/A

Documents

N/A

Functional Requirement

We are using the userexit which is already being for delivery creation for Outbound.
The enhancement is used to update Customer Partners from Sales Orders,Sales Org, Incoterm and Route value into Inbound delivery so that data is populated into ASN for Customer.
This userexit is triggered when Inbound program - ZSNC_INBOUND_DELV or T code VL31N (Manual Inbound creation ) or T code VL31 is executed.

This Enhancement will Update following values into Inbound delivery.
1) Customer Partners from Sales orders.
2) Goods Supplier from the PO in place of PO Vendor
3) Incoterms
4) Sales Organization data
5) Route (Customer Route from Sales order)

Note: If these above values are changed after the Inbound delivery is created , the latest updated values from the Inbound will populated into the ASN .

Solution Summary

[Discuss this section with Requester and get approval prior to beginning work]
We are using the user exit which is already being for delivery creation for Outbound.

Test Plan

[List test scenarios/cases to be executed here]

sl	User exit used	Test Scenario	Expected Results
1	No	Create Drop ship order, convert to PO and update the confirmations and create Inbound delivery with program and complete the PACKING and PGR process The ASN is triggered.	Check the delivery it does not sales order partners, incoterms , route , and also check the ASN Idoc and see if any related values are populated
2	Yes	Create Drop ship order, convert to PO and update the confirmations and create Inbound delivery using PROGRAM and complete the PACKING and PGR process The ASN is triggered.	Delivery should have all the values and also the ASN should populated these values in the Idoc
3	Yes	Create Drop ship order, convert to PO and update the confirmations and create Inbound delivery MANUALLY- VL31N and complete the PACKING and PGR process The ASN is triggered.	Delivery should have all the values and also the ASN should populated these values in the Idoc

Solution Details

[Provide complete technical details for configuration or programming here]

The enhancement - MV50AFZ1 is used to update Customer Partners from Sales Orders,Sales Org, Incoterm and Route value into Inbound delivery so that data is populated into ASN for Customer.
This user exit is triggered when Inbound program - ZSNC_INBOUND_DELV or T code VL31N (Manual Inbound creation ) or T code VL31 is executed.

This Enhancement will Update following values into Inbound delivery.
1) Customer Partners from Sales orders.
2) Goods Supplier from the PO in place of PO Vendor
3) Incoterms
4) Sales Organization data
5) Route (Customer Route from Sales order)

Note: If these above values are changed after the Inbound delivery is created , the latest updated values from the Inbound will populated into the ASN .

Issues

2014-01-30 - 6474 - Rel Notes - SNC Enhancement to get sales order details in Inbound delivery